home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 6
/
Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso
/
034a
/
hcrash13.zip
/
HOTCRASH.DOC
< prev
next >
Wrap
Text File
|
1991-12-14
|
13KB
|
281 lines
┌───────────────┐
│ HOTCrash 1.30 │
└───────────────┘
Copyright 1991 HOTware.
All Rights Reserved.
Current Version 1.30, Released December 14, 1991
┌──────────────┐
│ History │
└──────────────┘
11-26-91 Initial Release Version 1.00
11-27-91 Version 1.10: Lengthened the Call Window Modifier
Field from 10 Characters to 15 Characters.
12-01-91 Version 1.20: Bug Fix Release, Erroneous Nodes
were showing up in the OUTBOUND WINDOWS Section
of the Routing File.
12-14-91 Version 1.30: A Small MDRIVER Inconsistency was
found. If Reconsolidation was preformed on the
last OUTBOUND call, MDRIVER was not exiting even
though the /Q was placed on the command line.
HOTCrash now looks at the GTNETDAY.LOG file to
determine if all nodes have been connected with.
If ALL Nodes have been connected with, MDRIVER
will not be reloaded after the reconsolidation
on the final node.
┌──────────────┐
│ Notice │
└──────────────┘
The B.S. At The Start.....
THIS IS NOT FREE SOFTWARE and may not be sold without
the author's express written permission.
Some of the terms used in this document and programs used
in conjunction with HOTCrash are trademarks of the following:
GT POWER Copyright P&M Software
MDRIVER Copyright P&M Software
MBAGGER Copyright P&M Software
MDIST Copyright P&M Software
DSZ Copyright OMEN Technology
BIMODEM Copyright ERIC Labs
┌──────────────┐
│ Registration │
└──────────────┘
The non-commercial single-user registration fee for HOTCrash
is $10.00 US. If you would like to receive the latest version of
HOTCrash on diskette at the time of registration, please add $3.00
to the above stated registration amount.
Send a check or money order, of the appropriate amount to:
Rob Roesch
Rt 7 Box 566
Mocksville, NC 27028
All registrations must also include a completed registration
information form. The registration form will be found in the
HOTCrash archive. The form is named HCREG.FRM.
After registration is received you will receive the required CRC's
to unlock all functions and remove all instances of "UNREGISTERED"
and associated delays from the HOTCrash program.
┌─────────────┐
│ Purpose │
└─────────────┘
HOTCrash is a utility that acts as a front end to the MDRIVER program
as supplied by P&M Software when you registered GT Power. HOTCrash
allows you to configure up to 20 Net/Nodes that you commonly make
crash calls to. After these are installed, you can browse the list and
tag nodes that you would like to crash. You may be saying, "I can
already do this with a batch file". That you are correct, but HOTCrash
automates the process for you without any lengthy and complicated batch
files. In your configuration, described below, you will find an option
that allows you to specify the maximum amount of time that you would
like to remain in Crash Mode before giving up. HOTCrash will take the
current time, add the Max Crash Time, and build the appropriate times
to be placed on the MDriver Command line. These times will also be
calculated and a CALL WINDOWS Section will be built up in the temporary
routing file that is created by HOTCrash.
HOTCrash will also reconsolidate mail bags after each connect if you
wish. HOTCrash will look for an ErrorLevel of 255 to be passed from
MDRIVER after a successful connect with an outbound node. If this
errorlevel is received, HOTCrash will execute a batch file that you
have previously created named G_UNPAK.BAT. Here is an example of what
my G_UNPAK.BAT looks like......
MDIST /G
MBAGGER /NP /G /zx /X
This batch file will instruct MDIST to distribute Consolidated Bags
Only and Bag up Consolidated Bags Only. For further information on
these functions please review your Netmail Documentation. Of course
these options are configurable....
┌─────────────┐
│ Nets/Nodes │
└─────────────┘
The primary HOTCrash Screen will consist of 20 editable fields
in which you configure the NET/NODE's that you normally call
for CRASH Mail Transfers. The 20 fields all for two purposes.
The primary purpose is the Net/Node for calling. The secondary
purpose is to add and "Call Window Modifiers" that you would like
to apply when calling that particular Node. Below you will see
an example configuration....
┌───────────────────────┐ ┌───────────────────────┐
│064/001 'ATB1DT' │ │ / │
│033/016 'ATX3DT' │ │ / │
│052/003 /? │ │ / │
│ / │ │ / │
│ / │ │ / │
│ / │ │ / │
│ / │ │ / │
│ / │ │ / │
│ / │ │ / │
│ / │ │ / │
└───────────────────────┘ └───────────────────────┘
In the above example there are three nodes that are configured
for Crash Calls. If 064/001 were tagged, HOTCrash would put
a 'ATB1DT' on the call window for that Node. This would tell
MDRIVER to use this as a pre-dial string for this node, likewise
with 033/016. 052/003 uses a /? Call Window Modifier which tells
MDRIVER to only call 052/003 if they have not been connected with on
today's date. For further information on Call Window Modifiers
please consult your NETMAIL Documentation.....
┌───────────────┐
│ Configuration │
└───────────────┘
╔════════════════════════════════════════════════════════════════════════╗
║ ║
║ Reg Name: UN-Registered Reg. CRC:0000-0000 ║
║ ║
║ Netmail CRC: 0000-0000 Routing File: ROUTING.BBS Mail Drive: C ║
║ ║
║ DSZ Extension: EXE Use Bimodem?: N Call G_UNPAK?: Y ║
║ ║
║ MDRIVER Name: MDRIVER.COM MAX Crash Time 30 minutes ║
║ ║
║ ║
╚╡ F1 Help ESC Exit Config Next Field ALT D DOS Shell ╞══════════╝
Above you will see the HOTCrash main configuration screen. The options
in HOTCrash are fairly straight forward. I will explain each of them
now.....
1. Reg Name: This is the name that you have selected to register
HOTCrash Under. This name should be sent to the author by filling
in the Registration Form. This option is CaSe SeNsItIvE.
2. Reg. CRC: You will receive a Registered CRC from the author after
registration of this program. Registration will allow all of the
HOTCrash features to work fully...
3. Netmail CRC: This is the CRC That you received upon Registration of
GT Power. This is the CRC That is to be placed on the MDRIVER
Command line. If this CRC is incorrect, netmail transfers will be
aborted by MDRIVER.
4. ROUTING File: This is the name of the file the following sections
for use by MDriver: ROUTING INSTRUCTIONS, PURSUIT, PHONE NO
TRANSFORMS etc. Not all of these sections are required, but they
will be loaded into the temporary routing file if found. This file
*MUST* be in you GTPATH Directory.
5. MAIL DRIVE: This is the designator of the drive that contains the
MAILOUT and MAILIN directories that are used by the Netmail
Programs. HOTCrash will automatically switch to this drive prior to
loading Mdriver. If you are not always on the same drive when
running netmail, serious problems can occur.
6. DSZ Extension: MDRIVER has the capability of using either DSZ.COM
DSZ.EXE MEGALINK and BIMODEM to transfer mail bags. If you wish to
use DSZ, put the extension of the DSZ that you are using here (COM
or EXE). If you wish to use only MEGALINK leave this field blank
7. USE Bimodem?: MDRIVER also has the capability of using BIMODEM
from Eric Labs to do netmail transfers. If you wish to try BIMODEM
select 'Y' in this field.
8. Call G_UNPAK: This option will tell MDRIVER to reconsolidate mail
bags after each successful transfer. If you select Y to this option
HOTCrash will add a /G to the MDRIVER command line, thus telling
MDriver to exit 255 after a successful transfer. HOTCrash will read
this errorlevel and immediately load G_UNPAK.BAT. After the
completion of this batch file, Mdriver will be reloaded. For a
discussion on Reconsolidating mail bags please consult your Netmail
Documentation.
9. MDriver Name: Simply, what have you named your Mdriver Program?
This name is needed so that the file can be executed when you are
ready to make a crash call. This program MUST be in the GTPATH
Directory.
10. MAX Crash Time: How long do you want me to stay in Crash Mode if I
am unable to make all the connections? If all connections are made,
this time length will be shorter.....
This name is needed so that the file can be executed when you are
ready to make a crash call. This program MUST be in the GTPATH
Directory.
┌─────────────┐
│ Errorlevels │
└─────────────┘
HOTCrash will exit with the following errorlevels if something
happens during execution. These could be useful for batch file
operation:
Errorlevel 1: GTPATH Environment Variable Not Set.
Errorlevel 2: Unable To Open Specified Routing File.
Errorlevel 3: Cannot Find Configured MDRIVER.
Errorlevel 4: Fatal Error Reading Configuration.
┌─────────────┐
│ Support │
└─────────────┘
Although Unregistered Users support will be somewhat limited, I
do not want to leave them out in the cold. If you find any
problems with HOTCrash, would like to get registration
information, or version information, I can be reached at the
following....
HOTware
Rob Roesch
Rt 7 Box 566
Mocksville, NC 27028
VOICE (704) 492-2023
MODEM (704) 492-2081
(USRobotics V.32 9600)
┌────────────────┐
│Acknowledgements│
└────────────────┘
I would like to thank the following list of BETA testers
for their support and patience. Each of these folks have
had a special part of bringing about this release of
HOTCrash. I would especially like to think Jim Knight, 90%
of this program were his ideas and suggestions. I just put
them in EXE form.
Jim Knight
Steve Tucker